|
|
 |
|
|
|
|
frmMaintainWorkgroups form, 270 |
|
|
|
|
|
|
|
|
frmMDI form, 266, 280-281 |
|
|
|
|
|
|
|
|
implementation guidelines, 264 |
|
|
|
|
|
|
|
|
scenario scripts, 265 |
|
|
|
|
|
|
|
|
use case, 266-268 |
|
|
|
|
|
|
|
|
base classes, 13 |
|
|
|
|
|
|
|
|
baseline applications, 190 |
|
|
|
|
|
|
|
|
BasicPersonalChecking class |
|
|
|
|
|
|
|
|
adjustBalance method, 244 |
|
|
|
|
|
|
|
|
code listing, 180-184 |
|
|
|
|
|
|
|
|
BasicPersonalChecking-Account class, 137 |
|
|
|
|
|
|
|
|
BeCubed Software Web site, 158 |
|
|
|
|
|
|
|
|
beta testing, 173 |
|
|
|
|
|
|
|
|
Bickford, Peter, 291 |
|
|
|
|
|
|
|
|
binary access file management |
|
|
|
|
|
|
|
|
advantages, 382-383 |
|
|
|
|
|
|
|
|
Byte arrays, 382 |
|
|
|
|
|
|
|
|
disadvantages, 383-384 |
|
|
|
|
|
|
|
|
opening files, 383 |
|
|
|
|
|
|
|
|
persisting (saving) information, 383 |
|
|
|
|
|
|
|
|
retaining data integrity, 382 |
|
|
|
|
|
|
|
|
when to use, 382 |
|
|
|
|
|
|
|
|
BinaryFile class, 383, 387 |
|
|
|
|
|
|
|
|
black box controls, 159 |
|
|
|
|
|
|
|
|
Booch method, 68-69 |
|
|
|
|
|
|
|
|
boundaries (classes), 13 |
|
|
|
|
|
|
|
|
boundary class, 203 |
|
|
|
|
|
|
|
|
Break in Class Module option, 401-402 |
|
|
|
|
|
|
|
|
browsers, 290, 309, 330, 374 |
|
|
|
|
|
|
|
|
business |
|
|
|
|
|
|
|
|
analysts, reverse engineering, 223-224 |
|
|
|
|
|
|
|
|
classes |
|
|
|
|
|
|
|
|
collections, 451 |
|
|
|
|
|
|
|
|
defining, 339 |
|
|
|
|
|
|
|
|
handling data in, 337 |
|
|
|
|
|
|
|
|
modeling interactions among, 340 |
|
|
|
|
|
|
|
|
policy enforcement classes, 184 |
|
|
|
|
|
|
|
|
objects, 337 |
|
|
|
|
|
|
|
|
process models, 41 |
|
|
|
|
|
|
|
|
forward engineering, 223 |
|
|
|
|
|
|
|
|
reverse engineering, 223-227 |
|
|
|
|
|
|
|
|
processes |
|
|
|
|
|
|
|
|
automating, 291 |
|
|
|
|
|
|
|
|
defined, 41 |
|
|
|
|
|
|
|
|
dynamic nature of, 292 |
|
|
|
|
|
|
|
|
rules, 309 |
|
|
|
|
|
|
|
|
applications, managing, 177, 338 |
|
|
|
|
|
|
|
|
defined, 336 |
|
|
|
|
|
|
|
|
discovering, 340 |
|
|
|
|
|
|
|
|
enforcing, 336-338, 343-347 |
|
|
|
|
|
|
|
|
examples, 336 |
|
|
|
|
|
|
|
|
exceptions, 338, 344 |
|
|
|
|
|
|
|
|
identifying, 339 |
|
|
|
|
|
|
|
|
logic, 177-184, 340 |
|
|
|
|
|
|
|
|
OOP for enforcing, 336-337 |
|
|
|
|
|
|
|
|
Samsona Bank Teller System example, 177-184 |
|
|
|
|
|
|
|
|
testing constraints, 177-178, 184 |
|
|
|
|
|
|
|
|
validating assumptions, 339 |
|
|
|
|
|
|
|
|
work flow-related, 292 |
|
|
|
|
|
|
|
|
services, 30 |
|
|
|
|
|
|
|
|
tier, 336 |
|
|
|
|
|
|
|
|
Business Rules Subsystem |
|
|
|
|
|
|
|
|
classes, 342 |
|
|
|
|
|
|
|
|
development process, 337 |
|
|
|
|
|
|
|
|
implementing Object Model, 340 |
|
|
|
|
|
|
|
|
overview, 336 |
|
|
|
|
|
|
|
|
purpose, 337 |
|
|
|
|
|
|
|
|
Second Bank of Carollton example, 177, 340, 345-347 |
|
|
|
|
|
|
|
|
buttons, 249 |
|
|
|
|
|
|
|
|
Byte arrays, 382 |
|
|
|
|
|
|
|
|
Call Stack dialog box, 423 |
|
|
|
|
|
|
|
|
Cancel buttons, 249 |
|
|
|
|
|
|
|
|
CancelTransaction class, 273 |
|
|
|
|
|
|
|
|
candidate classes, 234 |
|
|
|
|
|
|
|
|
candidates (problem statements) |
|
|
|
|
|
|
|
|
actors, 45-47 |
|
|
|
|
|
|
|
|
classes, 45-47 |
|
|
|
|
|
|
|
|
defined, 44 |
|
|
|
|
|
|
|
|
verbs, 47-49 |
|
|
|
|
|
|
|
|
CApplication class, 312 |
|
|
|
|
|
|
|
|
declarations, 325 |
|
|
|
|
|
|
|
|
methods, 322 |
|
|
|
|
|
|
|
|
initializeSystem, 326 |
|
|
|
|
|
|
|
|
terminateSystem, 390 |
|
|
|
|
|
|
|
|
cardinality (relationships), 58 |
|
|
|
|
|
|
|
|
CashDepositRecord class, 343-344 |
|
|
|
|
|
|
|
|
CashDepositRecord method, 343 |
|
|
|
|
|
|
|
|
CashDepositRecord object, 344 |
|
|
|
|
|
|
|
|
CGI (common gateway interface), 8 |
|
|
|
|
|